Online banking digital wallet management

ABSTRACT

Embodiments are directed to digital wallet management. Embodiments initiate presentation of a digital wallet management interface, comprising initiating presentation of at least one digital wallet; and initiating presentation of at least one representation of at least one payment credential and at least one indication of which of the at least one digital wallets are associated with each of the at least one payment credentials.

CROSS-REFERENCE OF RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.14/196,383, filed Mar. 4, 2014 entitled “Online Banking Digital WalletManagement,” the contents of which are hereby incorporated by reference.

BACKGROUND

In the new technological age, the security of personal information, orthe lack thereof, has become an issue that concerns many people. As aresult, several business industries, such as financial institutions,have taken precautionary measures to ensure the safety and protection oftheir customers' information. This is typically accomplished byverifying a user's identity prior to transferring any personalinformation using an electronic means.

BRIEF SUMMARY

Embodiments of the invention are directed to an apparatus for digitalwallet management, whereby the apparatus provides a user a comprehensivemanagement platform for managing multiple digital wallets and theirassociated payment credentials, where the apparatus includes a memory; aprocessor; and a module stored in the memory, executable by theprocessor, and configured to initiate presentation of a digital walletmanagement interface, comprising initiating presentation of at least onedigital wallet; and initiating presentation of at least onerepresentation of at least one payment credential and at least oneindication of which of the at least one digital wallets are associatedwith each of the at least one payment credentials.

In some embodiments, the at least one representation of the at least onepayment credential comprises a graphical object representing the atleast one payment credential; the at least one representation of the atleast one digital wallet comprises a graphical object representing theat least one digital wallet; and the at least one indication comprises agraphical link between the graphical object representing the at leastone payment credential and the graphical object representing the atleast one digital wallet. In some such embodiments, the graphical linkcomprises an overlap of the graphical object representing the at leastone payment credential with the graphical object representing the atleast one digital wallet.

In some embodiments, the module is further configured to receive userinput selecting one of the at least one representations of the at leastone payment credentials; and receive user input selecting one of the atleast one digital wallets for association with the selected at least onepayment credential. In some such embodiments, the module is furtherconfigured to initiate presentation of the selected payment credentialand the selected digital wallet and at least one indication ofassociation between the selected payment credential and the selecteddigital wallet.

In some embodiments, the module is further configured to receive userinput setting a usage limit for one of the at least one digital wallets.In some such embodiments, the usage limit is a threshold spending limitfor an aggregation of all the payment credentials associated with thedigital wallet. In other such embodiments, the usage limit is athreshold spending limit to be applied to each of the paymentcredentials associated with the digital wallet individually.

In some embodiments, the usage limit is a threshold number oftransactions for an aggregation of all the payment credentialsassociated with the digital wallet.

In some embodiments, the usage limit is a threshold number oftransactions applied to each of the payment credentials associated withthe digital wallet individually.

In some embodiments, the usage limit is a timing limit to be applied toan aggregation of all the payment credentials associated with thedigital wallet.

In some embodiments, the usage limit is a timing limit to be applied toeach of the payment credentials associated with the digital wallet.

In some embodiments, the interface is accessed by a customerauthenticated through an online banking session administered by afinancial institution also administering the digital wallet. In otherembodiments, the interface is accessed by a customer authenticatedthrough a mobile banking application session administered by a financialinstitution also administering the digital wallet.

According to embodiments of the invention, a method for digital walletmanagement whereby the apparatus provides a user a comprehensivemanagement platform for managing multiple digital wallets and theirassociated payment credentials includes initiating presentation, by aprocessor, of a digital wallet management interface, comprising:initiating presentation of at least one digital wallet; and initiatingpresentation of at least one representation of at least one paymentcredential and at least one indication of which of the at least onedigital wallets are associated with each of the at least one paymentcredentials.

In some embodiments, the at least one representation of the at least onepayment credential comprises a graphical object representing the atleast one payment credential; the at least one representation of the atleast one digital wallet comprises a graphical object representing theat least one digital wallet; and the at least one indication comprises agraphical link between the graphical object representing the at leastone payment credential and the graphical object representing the atleast one digital wallet.

In some such embodiments, the graphical link comprises an overlap of thegraphical object representing the at least one payment credential withthe graphical object representing the at least one digital wallet.

According to embodiments of the invention, a computer program productfor digital wallet management, whereby the apparatus provides a user acomprehensive management platform for managing multiple digital walletsand their associated payment credentials, the computer program productcomprising a non-transitory computer-readable medium comprising codecausing a first apparatus to: initiate presentation of a digital walletmanagement interface, comprising: initiating presentation of at leastone digital wallet; and initiating presentation of at least onerepresentation of at least one payment credential and at least oneindication of which of the at least one digital wallets are associatedwith each of the at least one payment credentials.

In some embodiments, the at least one representation of the at least onepayment credential comprises a graphical object representing the atleast one payment credential; the at least one representation of the atleast one digital wallet comprises a graphical object representing theat least one digital wallet; and the at least one indication comprises agraphical link between the graphical object representing the at leastone payment credential and the graphical object representing the atleast one digital wallet.

In some embodiments, the graphical link comprises an overlap of thegraphical object representing the at least one payment credential withthe graphical object representing the at least one digital wallet.

BRIEF DESCRIPTION OF THE DRAWINGS

Having thus described embodiments of the invention in general terms,reference will now be made to the accompanying drawings, where:

FIG. 1 is a diagram illustrating a token system, in accordance withembodiments of the present invention;

FIG. 2 is a diagram illustrating a token system, in accordance withembodiments of the present invention;

FIG. 3 is a diagram illustrating a token system, in accordance withembodiments of the present invention;

FIG. 4 is a diagram illustrating an environment in which systemsaccording to embodiments of the invention operate;

FIG. 5 is a representation of an interface for managing digital walletsaccording to embodiments of the invention;

FIG. 6 is a flowchart illustrating a method for digital walletmanagement according to embodiments of the invention;

FIG. 7 is a flowchart illustrating a method for digital walletmanagement according to embodiments of the invention; and

FIG. 8 is a flowchart illustrating a method for digital walletmanagement according to embodiments of the invention.

DETAILED DESCRIPTION OF EMBODIMENTS OF THE INVENTION

Embodiments of the present invention now may be described more fullyhereinafter with reference to the accompanying drawings, in which some,but not all, embodiments of the invention are shown. Indeed, theinvention may be embodied in many different forms and should not beconstrued as limited to the embodiments set forth herein; rather, theseembodiments are provided so that this disclosure may satisfy applicablelegal requirements. Like numbers refer to like elements throughout.

In accordance with embodiments of the invention, the term “financialtransaction” or “transaction” refers to any transaction involvingdirectly or indirectly the movement of monetary funds throughtraditional paper transaction processing systems (i.e. paper checkprocessing) or through electronic transaction processing systems.Typical financial transactions include point of sale (POS) transactions,automated teller machine (ATM) transactions, internet transactions,electronic funds transfers (EFT) between accounts, transactions with afinancial institution teller, personal checks, etc. When discussing thattransactions are evaluated it could mean that the transaction hasalready occurred, is in the processing of occurring or being processed,or it has yet to be processed by one or more financial institutions. Insome embodiments of the invention the transaction may be a customeraccount event, such as but not limited to the customer changing apassword, ordering new checks, adding new accounts, opening newaccounts, etc.

In accordance with embodiments of the invention, the term “financialinstitution” refers to any organization in the business of moving,investing, or lending money, dealing in financial instruments, orproviding financial services. This includes commercial banks, thrifts,federal and state savings banks, savings and loan associations, creditunions, investment companies, merchants, insurance companies and thelike.

In accordance with embodiments of the invention the terms “customer” and“user” and “consumer” may be interchangeable. These terms may relate toa direct customer of the financial institution or person or entity thathas authorization to act on behalf of the direct customer, user, orconsumer (i.e., indirect customer).

Various embodiments of the present invention relate to tokenization,which is generally described in the area of financial transactions asutilizing a “token” (e.g., an alias, substitute, surrogate, or otherlike identifier) as a replacement for sensitive account information, andin particular account numbers. As such, tokens or portions of tokens maybe used as a stand in for a user account number, user name, pin number,routing information related to the financial institution associated withthe account, security code, or other like information relating to theuser account. The one or more tokens may then be utilized as a paymentinstrument to complete a transaction. The one or more tokens may beassociated with one or more payment devices directly or within one ormore digital wallets associated with the payment devices. In otherembodiments, the tokens may be associated with electronic transactionsthat are made over the Internet instead of using a physical paymentdevice. Utilizing a token as a payment instrument instead of actualaccount information, and specifically an account number, improvessecurity, and provides flexibility and convenience in controlling thetransactions, controlling accounts used for the transactions, andsharing transactions between various users.

Tokens may be single-use instruments or multi-use instruments dependingon the types of controls (e.g., limits) initiated for the token, and thetransactions in which the token is used as a payment instrument.Single-use tokens may be utilized once, and thereafter disappear, arereplaced, or are erased, while multi-use tokens may be utilized morethan once before they disappear, are replaced, or are erased.

Tokens may be 16-digit numbers (e.g., like credit, debit, or other likeaccount numbers), may be numbers that are less than 16-digits, or maycontain a combination of numbers, symbols, letters, or the like, and bemore than, less than, or equal to 16-characters. In some embodiments,the tokens may have to be 16-characters or less in order to becompatible with the standard processing systems between merchants,acquiring financial institutions (e.g., merchant financial institution),card association networks (e.g., card processing companies), issuingfinancial institutions (e.g., user financial institution), or the like,which are used to request authorization, and approve or denytransactions entered into between a merchant (e.g., a specific businessor individual user) and a user. In other embodiments of the invention,the tokens may be other types of electronic information (e.g., pictures,codes, or the like) that could be used to enter into a transactioninstead of, or in addition to, using a string of characters (e.g.,numbered character strings, alphanumeric character strings, symboliccharacter strings, combinations thereof, or the like).

A user may have one or more digital wallets on the user's paymentdevice. The digital wallets may be associated specifically with theuser's financial institution, or in other embodiments may be associatedwith a specific merchant, group of merchants, or other third parties.The user may associate one or more user accounts (e.g., from the sameinstitution or from multiple institutions) with the one or more digitalwallets. In some embodiments, instead of the digital wallet storing thespecific account number associated with the user account, the digitalwallet may store a token or allow access to a token (e.g., provide alink or information that directs a system to a location of a token), inorder to represent the specific account number during a transaction. Inother embodiments of the invention, the digital wallet may store some orall of the user account information (e.g., account number, user name,pin number, or the like), including the user account number, butpresents the one or more tokens instead of the user account informationwhen entering into a transaction with a merchant. The merchant may be abusiness, a person that is selling a good or service (hereinafter“product”), or any other institution or individual with which the useris entering into a transaction.

The digital wallet may be utilized in a number of different ways. Forexample, the digital wallet may be a device digital wallet, a clouddigital wallet, an e-commerce digital wallet, or another type of digitalwallet. In the case of a device digital wallet the tokens are actuallystored on the payment device. When the device digital wallet is used ina transaction the token stored on the device is used to enter into thetransaction with the merchant. With respect to a cloud digital walletthe device does not store the token, but instead the token is stored inthe cloud of the provider of the digital wallet (or another thirdparty). When the user enters into a transaction with a merchant,transaction information is collected and provided to the owner of thecloud to determine the token, and thus, how the transaction should beprocessed. In the case of an e-commerce digital wallet, a transaction isentered into over the Internet and not through a point of sale terminal.As was the case with the cloud digital wallet, when entering into atransaction with the merchant over the Internet the transactioninformation may be captured and transferred to the wallet provider(e.g., in some embodiments this may be the merchant or another thirdparty that stores the token), and the transaction may be processedaccordingly.

Specific tokens, in some embodiments, may be tied to a single useraccount, but in other embodiments, may be tied to multiple useraccounts, as will be described throughout this application. In someembodiments a single tokens could represent multiple accounts, such thatwhen entering into a transaction the user may select the token (ordigital wallet associated with the token) and select one of the one ormore accounts associated with the token in order to allocate thetransaction to a specific account. In still other embodiments, afterselection of the token by the user the system may determine the bestaccount associated with the token to use during the transaction (e.g.,most cash back, most rewards points, best discount, or the like). Inaddition, the tokens may be associated with a specific digital wallet ormultiple digital wallets as desired by the institutions or users.

Moreover, the tokens themselves, or the user accounts, individual users,digital wallets, or the like associated with the tokens, may havelimitations that limit the transactions that the users may enter intousing the tokens. The limitations may include, limiting the transactionsof the user to a single merchant, a group of multiple merchants,merchant categories, single products, a group a products, productcategories, transaction amounts, transaction numbers, geographiclocations, or other like limits as is described herein.

FIGS. 1 through 3 illustrate a number of different ways that the user 2may use one or more tokens in order to enter into a transaction, as wellas how the parties associated with the transaction may process thetransaction. FIG. 1, illustrates one embodiment of a token systemprocess 1, wherein the token system process 1 is used in associationwith a tokenization service 50. The tokenization service 50 may beprovided by a third-party institution, the user's financial institution,or another institution involved in a transaction payment process. Asillustrated in FIG. 1 (as well as in FIGS. 2 and 3), a user 2 mayutilize a payment device 4 (or in other embodiments a payment instrumentover the Internet) to enter into a transaction. FIG. 1 illustrates thepayment device 4 as a mobile device, such as a smartphone, personaldigital assistant, or other like mobile payment device. Other types ofpayment devices 4 may be used to make payments, such as but not limitedto an electronic payment card, key fob, a wearable payment device (e.g.,watch, glasses, or the like), or other like payment devices 4. As such,when using a payment device 4 the transaction may be made between thepoint of sale (POS) and the payment device 4 by scanning informationfrom the payment device 4, using near field communication (NFC) betweenthe POS and the payment device 4, using wireless communication betweenthe POS and the payment device 4, or using another other type ofcommunication between the POS and the payment device 4. When enteringinto an e-commerce transaction over the Internet, for example using thepayment device 4 or another device without a POS, a payment instrument(e.g., a payment application that stores the token) may be used to enterinto the transaction. The payment instrument may be the same as thetoken or digital wallet associated with the payment device 4, exceptthey are not associated with specific payment device. For example, thetoken or digital wallet may be associated with a payment applicationthat can be used regardless the device being used to enter into thetransaction over the Internet.

The token can be associated directly with the payment device 4, orotherwise, through one or more digital wallets associated with thepayment device 4. For example, the token may be stored on one or morepayment devices 4 directly, and as such any transaction entered into bythe user 2 with the one or more payment devices 4 may utilize the token.Alternatively, the payment device 4 may have one or more digital walletsstored on the payment device 4 that allow the user 2 to store one ormore user account numbers, or tokens associated with the user accountnumbers, on the one or more digital wallets. The user may select adigital wallet or account within the digital wallet in order to enterinto a transaction using a specific type of customer account. As such,the digital wallets may be associated with the user's issuing financialinstitutions 40, other financial institutions, merchants 10 with whichthe user enters into transactions, or a third party institutions thatfacilitates transactions between users 2 and merchants 10.

As illustrated in FIG. 1, a tokenization service 50 may be available forthe user 2 to use during transactions. As such, before entering into atransaction, the user 2 may generate (e.g., create, request, or thelike) a token in order to make a payment using the tokenization service50, and in response the tokenization service 50 provides a token to theuser and stores an association between the token and the user accountnumber in a secure token and account database 52. The token may bestored in the user's payment device 4 (e.g., on the digital wallet) orstored on the cloud or other service through the tokenization service50. The tokenization service 50 may also store limits (e.g., geographiclimits, transaction amount limits, merchant limits, product limits, anyother limit described herein, or the like) associated with the tokenthat may limit the transactions in which the user 2 may enter. Thelimits may be placed on the token by the user 2, or another entity(e.g., client, administrator, person, company, or the like) responsiblefor the transactions entered into by the user 2 using the accountassociated with the token. The generation of the token may occur at thetime of the transaction or well in advance of the transaction, as aone-time use token or multi-use token.

After or during creation of the token the user 2 enters into atransaction with a merchant 10 using the payment device 4 (or paymentinstrument over the Internet). In some embodiments the user 2 may usethe payment device 4 by itself, or specifically select a digital walletor user account stored within the digital wallet, to use in order toenter into the transaction. The token associated with payment device,digital wallet, or user account within the wallet is presented to themerchant 10 as payment in lieu of the actual user account number and/orother user account information. The merchant 10 receives the token,multiple tokens, and/or additional user account information for thetransaction. The merchant 10 may or may not know that the token beingpresented for the transaction is a substitute for a user account numberor other user account information. The merchant also capturestransaction information (e.g., merchant, merchant location, transactionamount, product, or the like) related to the transaction in which theuser 2 is entering with the merchant 10.

The merchant 10 submits the token (as well as any user accountinformation not substituted by a token) and the transaction informationfor authorization along the normal processing channels (also describedas processing rails), which are normally used to process a transactionmade by the user 2 using a user account number. In one embodiment of theinvention the acquiring financial institution 20, or any otherinstitution used to process transactions from the merchant 10, receivesthe token, user account information, and transaction information fromthe merchant 10. The acquiring financial institution 20 identifies thetoken as being associated with a particular tokenization service 50through the token itself or user account information associated with thetoken. For example, the identification of the tokenization service 50may be made through a sub-set of characters associated with the token, arouting number associated with the token, other information associatedwith the token (e.g., tokenization service name), or the like. Theacquiring financial institution 20 may communicate with the tokenizationservice 50 in order to determine the user account number associated withthe token. The tokenization service 50 may receive the token andtransaction data from the acquiring financial institution 20, and inresponse, provide the acquiring financial institution 20 the useraccount number associated with the token as well as other userinformation that may be needed to complete the transaction (e.g., username, issuing financial institution routing number, user account numbersecurity codes, pin number, or the like). In other embodiments, iflimits have been placed on the token, the tokenization service 50 maydetermine whether or not the transaction information meets the limitsand either allows or denies the transaction (e.g., provides the useraccount number or fails to provide the user account number). Theembodiment being described occurs when the token is actually stored onthe payment device 4. In other embodiments, for example, when the actualtoken is stored in a cloud the payment device 4 may only store a link tothe token or other token information that allows the merchant 10 oracquiring financial institution to acquire the token from a stored cloudlocation.

If the acquiring financial institution 20 receives the user accountnumber from the tokenization service 50 (e.g., the tokenization serviceindicates that the transaction meets the limits), then the acquiringfinancial institution 20 thereafter sends the user account number, theother user information, and the transaction information directly to theissuing financial institution 40, or otherwise indirectly through thecard association networks 30. The issuing financial institution 40determines if the user 2 has the funds available to enter into thetransaction, and if the transaction meets other limits on the useraccount, and responds with approval or denial of the transaction. Theapproval runs back through the processing channels until the acquiringfinancial institution 20 provides approval or denial of the transactionto the merchant 10 and the transaction between the merchant 10 and theuser 2 is completed. After the transaction is completed the token may bedeleted, erased, or the like if it is a single-use token, or stored forfurther use if it is a multi-use token.

Instead of the process described above, in which the acquiring financialinstitution 20 requests the token from the tokenization service 50, insome embodiments the tokenization service 50 may receive the transactionrequest and transaction information from the merchant 10 or acquiringfinancial institution 20. Instead of providing the account number to theacquiring financial institution 20, the tokenization service 50 may sendthe transaction request and transaction information to the issuingfinancial institution 40 directly, or indirectly through the paymentassociation networks 30.

The embodiment illustrated in FIG. 1 prevents the user account numberand other user information from being presented to the merchant 10;however, the tokenization service 50, acquiring financial institution20, the card association networks 30, and the issuing financialinstitution 40 may all utilize the actual user account number and otheruser information to complete the transaction.

FIG. 2 illustrates another embodiment of a token system process 1, inwhich the user 2 may utilize a payment device 4 (or payment instrumentover the Internet) to enter into transactions with merchants 10utilizing tokens instead of user account numbers. As illustrated in FIG.2, the user may have one or more tokens, which may be associated withthe payment device 4, one or more digital wallets within the paymentdevice 4, or one or more user accounts associated with the digitalwallets. The one or more tokens may be stored in the user's paymentdevice 4 (or on the digital wallet), or stored on a cloud or otherservice through the issuing financial institution 40 or anotherinstitution. The user 2 may set up the digital wallet by communicatingwith the issuing financial institution 40 (e.g., the user's financialinstitution) to request a token for the payment device, either for thedevice itself, or for one or more digital wallets or one or more useraccounts stored on the payment device. As previously discussed, a walletmay be specifically associated with a particular merchant (e.g.,received from the merchant 10) and include one or more tokens providedby the issuing financial institution 40 directly (or through themerchant as described with respect to FIG. 3). In other embodiments, theissuing financial institution 40 may create the digital wallet for theuser 2 (e.g., through a wallet created for a business client or retailclient associated with the user 2) and include one or more tokens forvarious types of transactions, products, or the like. The issuingfinancial institution 40 may store the tokens, the associated useraccount information (e.g., including the user account number), and anylimits on the use of the tokens, as was previously described withrespect to the tokenization service 50 in FIG. 1. In one embodiment thetokens may include user account information or routing informationwithin the token or tied to the token, which allows the merchants 10 andother institutions in the payment processing systems to route the tokenand the transaction information to the proper institutions forprocessing. In other embodiments a tokenization routing database 32 maybe utilized to determine where to route a transaction using a token, asdescribed in further detail later.

The user 2 may enter into a transaction with the merchant 10 using apayment device 4 (or a payment instrument through the Internet). In oneembodiment the user 2 may enter into the transaction with a tokenassociated with the payment device 4 itself (or a payment instrumentthrough the Internet). In other embodiments, a specific digital walletand/or a specific account within the digital wallet may be selected fora particular merchant with whom the user 2 wants to enter into atransaction. For example, the user 2 may select “wallet 1” to enter intoa transaction with “merchant 1” and “token 1” to utilize a specificaccount. The merchant 10 identifies the token, and sends the token andthe transaction information to the acquiring financial institution 20.If the token has routing information the acquiring financial institution20 may route the token and transaction data to the issuing financialinstitution 40 directly or through the card association networks 30. Insituations where the token does not have associated routing information,the acquiring financial institution 20 may utilize a tokenizationrouting database 32 that stores tokens or groups of tokens and indicatesto which issuing financial institutions 40 the tokens should be routed.One or more of the acquiring financial institutions 20, the cardassociation networks 30, and/or the issuing financial institutions 40may control the tokenization routing database in order to assign andmanage routing instructions for tokenization across the paymentprocessing industry. The tokenization routing database 32 may bepopulated with the tokens and the corresponding issuing financialinstitutions 40 to which transactions associated with the tokens shouldbe routed. However, in some embodiments no customer account informationwould be stored in this tokenization routing database 32, only theinstructions for routing particular tokens may be stored.

Once the token and transaction details are routed to the issuingfinancial institution 40, the issuing financial institution 20determines the user account associated with the token through the use ofthe token account database 42. The financial institution determines ifthe funds are available in the user account for the transaction and ifthe transaction information meets other limits by comparing thetransaction information with the limits associated with the token, theuser account associated with the token, or other limits describedherein. If the transaction meets the limits associated with the token oruser account, then the issuing financial institution 20 allows thetransaction. If the transaction information does not meet one or more ofthe limits, then the issuing financial institution 20 denies thetransaction. The issuing financial institution sends a notification ofthe approval or denial of the transaction back along the channels of thetransaction processing system to the merchant 10, which either allows ordenies the transaction.

The embodiment illustrated in FIG. 2 allows the user and the financialinstitution to shield the user's account number and other userinformation from all of the entities in the payment processing systembecause the merchant 10, acquiring merchant bank 20, payment associationnetworks 30, or other institutions in the payment processing system onlyuse the token and/or other shielded user information to process thetransaction. Only the issuing financial institution 40 has the actualaccount number of the user 2.

FIG. 3 illustrates another embodiment of the token system process 1, inwhich the user 2 may utilize a payment device 4 (or payment instrumentover the Internet) to enter into transactions with a merchant 10utilizing a token instead of a user account number and/or other useraccount information. As illustrated in FIG. 3, the user 2 may have oneor more tokens associated with the payment device 2, the one or moredigital wallets, or one or more user accounts within the digitalwallets. The one or more tokens may be stored in the user's paymentdevice 4 (or within the digital wallet), or stored on a cloud or otherservice through the issuing financial institution 40 or anotherinstitution. The user 2 may set up the digital wallet by communicatingwith the issuing financial institution 40 (e.g., the user's financialinstitution) and/or the merchant 10 to request a token for the paymentdevice 4, either for the payment device 4 itself, for the one or moredigital wallets stored on the payment device 4, or for user accountswithin the digital wallet. The financial institution 40 may have adedicated group of tokens that are associated with a specific merchant,and as such the merchant 10 and the issuing financial institution 40 maycommunicate with each other to provide one or more tokens to the user 2that may be specifically associated with the merchant 10. For example,the issuing financial institution may provide a set of tokens to“merchant 1” to associate with “wallet 1” that may be used by one ormore users 2. As such “Token 10” may be associated with “wallet 1” andbe specified only for use for transactions with “merchant 1.”

The merchant 10 may provide the specific tokens from the financialinstitution 40 to the user 2, while the financial institution 40 maystore the user account information with the token provided to the user2. The financial institution may communicate directly with the user 2,or through the merchant 10 in some embodiments, in order to associatethe token with the user 2. Since the merchant 10 provides, or is atleast notified by the financial institution 40, that a specific token,or groups of tokens, are associated with a specific issuing financialinstitution 40, then the merchant 10 may associate routing informationand transaction information with the token when the user 2 enters into atransaction with the merchant 10 using the token.

The merchant 10 passes the token (and potentially other user accountinformation), routing information, and transaction information to theacquiring financial institution 20 using the traditional paymentprocessing channels. The acquiring financial institution 20, in turn,passes the token (and potentially other user account information) andtransaction information to the issuing financial institution 40directly, or indirectly through the payment association networks 30using the routing information. The issuing financial institution 40accesses the token and account database 42 to identify the user accountassociated with the token and determines if the transaction informationviolates any limits associated with the token or the user account. Theissuing financial institution 40 then either approves or denies thetransaction and sends the approval or denial notification back throughthe payment processing system channels to the merchant 10, which thennotifies the user 2 that the transaction is allowed or denied.

As is the case with the token system process 1 in FIG. 2, the tokensystem process 1 in FIG. 3 allows the user 2 and the financialinstitution 40 to shield the user's account number and other userinformation from all of the entities in the payment processing systembecause the merchant 10, acquiring merchant bank 20, payment associationnetworks 30, or other institutions in the payment processing system onlyuse the token and/or other shielded user information to process thetransaction. Only the issuing financial institution 40 has the actualaccount number of the user 2.

The embodiments of the invention illustrated in FIGS. 1 through 3 areonly example embodiments of the invention, and as such it should beunderstood that combinations of these embodiments, or other embodimentsnot specifically described herein may be utilized in order to processtransactions between a user 2 and merchant 10 using one or more tokensas a substitute for user account numbers or other user accountinformation, such that the merchant 10, or other institutions in thepayment processing system do not have access to the actual user accountsor account information.

As briefly discussed above, if the issuing financial institution 40creates the digital wallet not only does the issuing financialinstitution 40 receive transaction information along the normalprocessing channels, but the financial institution 50 may also receiveadditional transaction information from the user 2 through the digitalwallet using the application program interfaces (APIs) or otherapplications created for the digital wallet. For example, geographiclocation information of the user 2, dates and times, productinformation, merchant information, or any other information may betransmitted to the issuing financial institution 40 through the APIs orother applications to the extent that this information is not alreadyprovided through the normal transaction processing channels. Thisadditional transaction information may assist in determining if thetransactions meet or violate limits associated with the tokens, useraccounts, digital wallets, or the like.

Alternatively, if the merchant 10 or another institution, other than theissuing financial institution 40, provides the digital wallet to theuser 2, the issuing financial institution 40 may not receive all thetransaction information from the traditional transaction processingchannels or from the digital wallet. As such, the issuing financialinstitution 40 may have to receive additional transaction informationfrom another application associated with the user 2 and compare thetransaction information received through the traditional channels inorder to associate the additional information with the transaction. Inother embodiments, the issuing financial institutions 40 may havepartnerships with the merchants 10 or other institutions to receiveadditional transaction information from the digital wallets provided bythe merchants or other institutions when the users 2 enter intotransactions using the digital wallets.

Moreover, when there is communication between the digital wallets of theusers 2 and the issuing financial institution 40 or another institution,transactions in which the user 2 may enter may be pre-authorized (e.g.,pre-qualified) to determine what accounts (e.g., tokens) may be used tocomplete the transaction, without having to arbitrarily choose anaccount for the transaction. In the case when there are multiple digitalwallets or multiple accounts, the account that is pre-authorized or theaccount that provides the best rewards may be automatically chosen tocomplete the transactions.

Additional embodiments of the invention will now be described in furtherdetail in order to provide additional concepts and examples related tohow tokens may be utilized in these illustrated token system processes 1or in other token system processes not specifically described in FIGS. 1through 3.

Referring to FIG. 4, a network environment is illustrated in accordancewith embodiments of the present invention. As illustrated in FIG. 4, theremote server 402 is operatively coupled via a network 401 to the mobiledevice 404 and/or a point of transaction (POT) 406. In thisconfiguration, the remote server 402 may send information to and receiveinformation from the mobile device 404 and/or the POT 406. Additionally,the mobile device 404 may send and receive communications directly fromthe POT 406. The remote server 402 may be or include one or more networkbase stations or other network components. FIG. 4 illustrates only oneexample of an embodiment of a network environment 400, and it will beappreciated that in other embodiments one or more of the systems,devices, or servers may be combined into a single system, device, orserver, or be made up of multiple systems, devices, or server.

The network 401 may be a global area network (GAN), such as theInternet, a wide area network (WAN), a local area network (LAN), atelecommunication network or any other type of network or combination ofnetworks. The network 401 may provide for wireline, wireless, or acombination wireline and wireless communication between devices on thenetwork 401.

In some embodiments, the user 405 is an individual who maintainscellular products with one or more providers.

As illustrated in FIG. 4, the remote server 402 generally comprises acommunication device 450, a processing device 452, and a memory device454. As used herein, the term “processing device” generally includescircuitry used for implementing the communication and/or logic functionsof the particular system. For example, a processing device may include adigital signal processor device, a microprocessor device, and variousanalog-to-digital converters, digital-to-analog converters, and othersupport circuits and/or combination of the foregoing. Control and signalprocessing functions of the system are allocated between theseprocessing devices according to their respective capabilities. Theprocessing device may include functionality to operate one or moresoftware programs based on computer readable instructions thereof, whichmay be stored in a memory device.

The processing device 452 is operatively coupled to the communicationdevice 450 to communicate with the network 401 and other devices on thenetwork 401. As such, the communication device 450 generally comprises amodem, server, or other device for communicating with other devices onthe network 401.

As further illustrated in FIG. 4, the network remote server 402comprises computer readable instructions 458 of an application 460. Insome embodiments, the memory device, 454 includes data storage 456 forstoring data related to and/or used by the application 460. Theapplication 460 may perform one or more of the steps and/or sub-stepsdiscussed herein and/or one or more steps not discussed herein. Forexample, in some embodiments, the application 460 may initiatepresentation of an interface for digital wallet management.

As illustrated in FIG. 4, the mobile device 404 generally comprises acommunication device 430, a processing device 432, and a memory device434. The processing device 432 is operatively coupled to thecommunication device 430 and the memory device 434. In some embodiments,the processing device 432 may send or receive data from the mobiledevice 404, to the remote server 402 via the communication device 430over a network 401. As such, the communication device 430 generallycomprises a modem, server, or other device for communicating with otherdevices on the network 401.

As further illustrated in FIG. 4, the mobile device 404 comprisescomputer readable instructions 438 stored in the memory device 434,which in one embodiments includes the computer-readable instructions 438of an application 440. In the embodiment illustrated in FIG. 4, theapplication 440 allows the mobile device 404 to be linked to the remoteserver 402 to communicate, via a network 401. The application 440 mayalso allow the mobile device to connect directly (i.e. locally or deviceto device) with the POT 406 for performing a transaction. Theapplication 440 may perform one or more of the steps and/or sub-stepsdiscussed herein and/or one or more steps not discussed herein. Forexample, in some embodiments, the application 440 may initiatepresentation of an interface for digital wallet management.

As illustrated in FIG. 4, the POT 406 may include a communication device410, a processing device 412, and a memory device 414. The processingdevice 412 is operatively coupled to the communication device 410 andthe memory device 414. In some embodiments, the processing device 412may send or receive data from the mobile device 404 and/or the remoteserver 402 via the communication device 410. Such communication may beperformed either over a direct connection and/or over a network 401. Assuch, the communication device 410 generally comprises a modem, server,or other device for communication with other devices on the network 401.

As further illustrated in FIG. 4, the POT 406, comprisescomputer-readable instructions 418 of an application 420. In theembodiment illustrated in FIG. 4, the application 420 allows the ATM 406to be linked to the remote server 402 to communicate, via a network 401.The application 420 may also allow the mobile device 406 to connectdirectly (i.e., locally or device to device) with the POT 406 orindirectly through the network 401. The application 420 may perform oneor more of the steps and/or sub-steps discussed herein and/or one ormore steps not discussed herein.

It is understood that the servers, systems, and devices described hereinillustrate one embodiment of the invention. It is further understoodthat one of more of the server, systems, and devices can be combined inother embodiments and still function in the same or similar way as theembodiments described herein.

In various embodiments, the POT device may be or include a merchantmachine and/or server and/or may be or include the mobile device of theuser may function as a point of transaction device. The embodimentsdescribed herein may refer to the use of a transaction, transactionevent or point of transaction event to trigger the steps, functions,routines etc. described herein. In various embodiments, occurrence of atransaction triggers the sending of information such as alerts and thelike. Unless specifically limited by the context, a “transaction”,“transaction event” or “point of transaction event” refers to anycommunication between the user and the merchant, e.g. financialinstitution, or other entity monitoring the user's activities. In someembodiments, for example, a transaction may refer to a purchase of goodsor services, a return of goods or services, a payment transaction, acredit transaction, or other interaction involving a user's bankaccount. As used herein, a “bank account” refers to a credit account, adebit/deposit account, or the like. Although the phrase “bank account”includes the term “bank,” the account need not be maintained by a bankand may, instead, be maintained by other financial institutions. Forexample, in the context of a financial institution, a transaction mayrefer to one or more of a sale of goods and/or services, an accountbalance inquiry, a rewards transfer, an account money transfer, openinga bank application on a user's computer or mobile device, a useraccessing their e-wallet or any other interaction involving the userand/or the user's device that is detectable by the financialinstitution. As further examples, a transaction may occur when an entityassociated with the user is alerted via the transaction of the user'slocation. A transaction may occur when a user accesses a building, usesa rewards card, and/or performs an account balance query. A transactionmay occur as a user's mobile device establishes a wireless connection,such as a Wi-Fi connection, with a point-of-sale terminal. In someembodiments, a transaction may include one or more of the following:purchasing, renting, selling, and/or leasing goods and/or services(e.g., groceries, stamps, tickets, DVDs, vending machine items, etc.);withdrawing cash; making payments to creditors (e.g., paying monthlybills; paying federal, state, and/or local taxes and/or bills; etc.);sending remittances; transferring balances from one account to anotheraccount; loading money onto stored value cards (SVCs) and/or prepaidcards; donating to charities; and/or the like.

In some embodiments, the transaction may refer to an event and/or actionor group of actions facilitated or performed by a user's device, such asa user's mobile device. Such a device may be referred to herein as a“point-of-transaction device”. A “point-of-transaction” could refer toany location, virtual location or otherwise proximate occurrence of atransaction. A “point-of-transaction device” may refer to any deviceused to perform a transaction, either from the user's perspective, themerchant's perspective or both. In some embodiments, thepoint-of-transaction device refers only to a user's device, in otherembodiments it refers only to a merchant device, and in yet otherembodiments, it refers to both a user device and a merchant deviceinteracting to perform a transaction. For example, in one embodiment,the point-of-transaction device refers to the user's mobile deviceconfigured to communicate with a merchant's point of sale terminal,whereas in other embodiments, the point-of-transaction device refers tothe merchant's point of sale terminal configured to communicate with auser's mobile device, and in yet other embodiments, thepoint-of-transaction device refers to both the user's mobile device andthe merchant's point of sale terminal configured to communicate witheach other to carry out a transaction.

As used herein, a “user device” or “mobile device” may be apoint-of-transaction device as discussed, or may otherwise be a devicecarried by a user configured to communicate across a network such as acellular network, wireless fidelity network or otherwise. As used here a“user” refers to a previous customer or a non-customer of one or moremerchants or entities associated with one or more merchants.

In some embodiments, a point-of-transaction device is or includes aninteractive computer terminal that is configured to initiate, perform,complete, and/or facilitate one or more transactions. Apoint-of-transaction device could be or include any device that a usermay use to perform a transaction with an entity, such as, but notlimited to, an ATM, a loyalty device such as a rewards card, loyaltycard or other loyalty device, a magnetic-based payment device (e.g., acredit card, debit card, etc.), a personal identification number (PIN)payment device, a contactless payment device (e.g., a key fob), a radiofrequency identification device (RFID) and the like, a computer, (e.g.,a personal computer, tablet computer, desktop computer, server, laptop,etc.), a mobile device (e.g., a smartphone, cellular phone, personaldigital assistant (PDA) device, MP3 device, personal GPS device, etc.),a merchant terminal, a self-service machine (e.g., vending machine,self-checkout machine, etc.), a public and/or business kiosk (e.g., anInternet kiosk, ticketing kiosk, bill pay kiosk, etc.), a gaming device,and/or various combinations of the foregoing.

In some embodiments, a point-of-transaction device is operated in apublic place (e.g., on a street corner, at the doorstep of a privateresidence, in an open market, at a public rest stop, etc.). In otherembodiments, the point-of-transaction device is additionally oralternatively operated in a place of business (e.g., in a retail store,post office, banking center, grocery store, factory floor, etc.). Inaccordance with some embodiments, the point-of-transaction device is notowned by the user of the point-of-transaction device. Rather, in someembodiments, the point-of-transaction device is owned by a mobilebusiness operator or a point-of-transaction operator (e.g., merchant,vendor, salesperson, etc.). In yet other embodiments, thepoint-of-transaction device is owned by the financial institutionoffering the point-of-transaction device providing functionality inaccordance with embodiments of the invention described herein.

Referring now to FIG. 5, a diagram illustrates an example of aninterface for managing digital wallets. The example interfaceillustrates a combined representation of three digital walletsassociated with the mobile device of a user. As shown, each of thedigital wallets has at least one associated payment credential (e.g.,tokens). The tokens, as shown, are sorted into different digitalwallets. As shown, each of the digital wallets is also illustratedgraphically as a separate entity. Also shown is a comprehensive listingof the tokens available for usage, and therefore, available forassociation and/or authentication into one or more digital wallets. Thecustomer may select a token from the available token listing and thenassociate it with a particular wallet by dragging it into the graphicalrepresentation of the wallet. In other embodiments, once a token and/orwallet has been selected additional functionality is available, such asthat described below with reference to FIGS. 7 and/or 8.

According to embodiments of the invention, during an online bankingsession, a customer may use an interface to select which paymentcredentials (cards (credit/debit), tokens etc.) are entered into whichdigital wallets (e.g., google, paypal etc.). In some instances, thecustomer is given an opportunity to set limits for each wallet, and insome cases, the customer is provided an opportunity to set timeframelimits. The customer may use an interface for visibility into everywherea payment credential (e.g., credit/debit card) is tied for payment,recurring or otherwise. In a digital wallet, the customer may providerecurring payment information, and “push-button billpay enrollment”.

Referring now to FIG. 6, a flowchart illustrates a method 600 fordigital wallet management according to embodiments of the invention.

The first step, represented by block 610, is to initiate presentation ofa digital wallet management interface. This interface, in someembodiments, is presented on a mobile device of a customer of afinancial institution. The next step, represented by block 620, is toinitiate presentation of at least one digital wallet. The digitalwallet(s) may be presented in a variety of formats, such as a scrollingformat, multiple icons, or a flip-book format where the user may turnpages or leafs associated with each digital as if turning the pages of abook. Next, represented by block 630, the system initiates presentationof at least one representation of at least one payment credential and atleast one indication of which of the at least one digital wallets areassociated with each of the at least one payment credentials. Eachdigital wallet may be displayed concurrently, or in some embodiments,may include presentation of only a portion of the available digitalwallets, for example, only one or two digital wallets of many availabledigital wallets. In some embodiments, the payment credentials associatedwith a digital wallet may be overlaid on the associated digital walletthereby indicated the payment credential is associated with the digitalwallet. In some cases, a payment credential may be associated with morethan one digital wallet. In such a case, the payment credential may havean associated icon or representation shown with each of its associateddigital wallets. In some embodiments, on the other hand, the interfaceis payment credential-centric, or in other words, each paymentcredential is shown separately and the digital wallet(s) to which thepayment credential is associated are shown as objects within orotherwise associated with the payment credential. For example, a creditcard icon may be shown as a window that includes multiple objectsrepresenting the various digital wallets with which the credit card isassociated for use.

As used herein, when a payment credential is “associated with” a digitalwallet, the payment credential is typically shown by the interface to beconnected with the digital wallet for use as a payment credential withthe digital wallet. In such a case, the payment credential has been“authenticated for use” in association with the digital wallet such thatthe user may select the digital wallet for performing a transactionusing the associated payment credential. Authentication may require oneor more authentication steps with the financial institution that issuedthe payment credential. As discussed in further detail below, a paymentcredential may be authenticated for use with a digital wallet but may bede-selected for use with the digital wallet by the user (i.e., it maynot be associated with the digital wallet), in which case, the userwould not be allowed by the system to use the payment credential in atransaction with the digital wallet regardless of the fact that it hasbeen authenticated for use with the digital wallet. In such a case, theuser can use the interface to associate the already authenticatedpayment credential with the digital wallet and then perform the desiredtransaction.

In some embodiments, as represented by block 640, user input is receivedselecting one of the at least one representations of the at least onepayment credentials. Next, as represented by block 650, the systeminitiates presentation of the selected payment credential and theselected digital wallet and at least one indication of associationbetween the selected payment credential and the selected digital wallet.In some embodiments, as discussed above, the interface may be paymentcredential-centric or digital wallet-centric in that either the paymentcredential(s) or the digital wallet(s) serve as the “bins” in which thedigital wallet(s) and payment credential(s), respectively, may bemanipulated. Accordingly, the user may, in some embodiments, click anddrag desired icons into the desired bins in order to associate thepayment credentials and digital wallets. This may trigger one or morenecessary steps, such as authentication of the selected paymentcredential with the financial institution that issued the paymentcredential and/or authentication or other verification with the entitythat maintains/issues/facilitates the digital wallet.

In some embodiments, one or more of the payment credentials may be“authenticated” for use with a digital wallet but may not be selectedfor use with the digital wallet. In such cases, the authenticatedpayment credentials may not be shown as associated with the digitalwallet, but rather may reside in a queue bin or other bin. Some separateindicator may be used to indicate that the payment credential isauthenticated for use in a digital wallet for which it is not currentlyassociated (i.e., the digital wallet bin does not show that the paymentcredential is associated). In such a case, when the user selects thepayment credential for association with the digital wallet, then lessthan full authentication or no additional authentication may be requiredfor the payment credential to be associated with the digital wallet dueto the previous authentication of the payment credential with thedigital wallet.

In various embodiments, the at least one representation of the at leastone payment credential includes a graphical object representing the atleast one payment credential. Furthermore, in some embodiments, the atleast one representation of the at least one digital wallet comprises agraphical object representing the at least one digital wallet.Similarly, in some embodiments, the at least one indication comprises agraphical link between the graphical object representing the at leastone payment credential and the graphical object representing the atleast one digital wallet. The graphical link, in some embodiments, mayinclude an overlap of the graphical object representing the at least onepayment credential with the graphical object representing the at leastone digital wallet. In various other embodiments, the graphical link maybe one or more other graphical representations of a connection orassociation between the payment credential and the digital wallet (e.g.,one or more graphical similarities of the respective representations).

In various embodiment, the system is configured to receive user inputsetting a usage limit for one of the at least one digital wallets. Thisusage limit may be a threshold spending limit. Such a threshold spendinglimit may reference an aggregation of all the payment credentialsassociated with the digital wallet. In some instances, the usage limitis a threshold spending limit to be applied to each of the paymentcredentials associated with the digital wallet individually. In othercases, the usage limit is a threshold number of transactions for anaggregation of all the payment credentials associated with the digitalwallet. In various embodiments, the usage limit is or includes athreshold number of transactions applied to each of the paymentcredentials associated with the digital wallet individually.

In various embodiments, the usage limit is a timing limit to be appliedto an aggregation of all the payment credentials associated with thedigital wallet. In other embodiments, the usage limit is a timing limitto be applied to each of the payment credentials associated with thedigital wallet.

In some embodiments, the digital wallet management interface is accessedby a customer authenticated through an online banking sessionadministered by a financial institution also administering the digitalwallet. In some embodiments, the interface is accessed by a customerauthenticated through a mobile banking application session administeredby a financial institution also administering the digital wallet.

According to embodiments of the invention, a customer can operate“toggles” or switches that turn on/off token functionality for varioussituations. For example, the customer may turn on the “travel toggle”,which indicates that the customer is traveling. A token may be changedand then, when the “toggle” is removed, the token may be changed again.

Referring now to FIG. 7, a flowchart illustrates a method 700 for tokenmanagement according to embodiments of the invention. The method 700includes, as represented by block 710, initiating presentation of adigital wallet. The next step, represented by block 720, is to initiatepresentation of an original token associated with the digital wallet.Finally, as represented by block 730, the system initiates presentationof a toggle switch comprising a first position and a second position.

The toggle switch is associated with the original token and isconfigured for graphical manipulation by the user. The toggle switch mayhave a first and a second position in some embodiments, where the firstposition corresponds to the original token being available for use as apayment credential, and the second position corresponds to the originaltoken being unavailable for use as a payment credential.

In various embodiments, a travel indicator may be configured such thatthe first position corresponds to the user not traveling and the secondposition corresponds to the user traveling. In some cases, when thetravel indicator is moved from the first position to the secondposition, the original token is deactivated and a new token is issued tothe digital wallet.

In some embodiments, when the travel indicator is moved from the secondposition to the first position, the new token is deactivated and theoriginal token is re-activated. In some cases, when the travel indicatoris moved from the second position to the first position, the new tokenis deactivated and the second new token is issued to the digital wallet.In some embodiments, the system destroys the original token and/or thenew token.

In some embodiments, there may be multiple toggle switches associatedwith a single payment credential. In some cases, each of the toggleswitches may be locked or immovable by the customer based on whether thefinancial institution or other administering entity allows the togglesto be moved in a particular situation. For example, in some cases, atoggle switch may be associated with traveling, and if it is determinedthe customer is not traveling (based on, e.g., GPS data), then thetoggle switch may be disengaged or immovable by the customer. In someembodiments, the system may propose a particular toggle switch positionto the customer via the interface. For example, when it is determinedthat the customer is traveling (e.g., by using GPS data), then theinterface may propose that a travel toggle switch should be activated.Once the user confirms that the user is traveling, then the systemactivates the travel toggle switch, or in some cases, the user thenactivates the travel toggle switch manually.

According to embodiments of the invention, a payment credential-centricinterface provides the customer visibility into every payment obligation(one time, recurring or otherwise) associated with a payment credentialby providing information and management opportunities. The interface mayalso provide recurring payment information, and “push-button billpayenrollment”.

Referring now to FIG. 8, a flowchart illustrates a method 800 forcredential management according to embodiments of the invention. Thefirst step, as represented by block 810 is to determine one or morepayment obligations associated with a payment credential. The next step,represented by block 820, is to initiate presentation of a paymentcredential management interface. Next, as represented by block 830, thesystem initiates presentation of a representation of the paymentcredential. Finally, as represented by block 840, the system initiatespresentation of the one or more payment obligations associated with thepayment credential.

In some embodiments, determining the one or more payment obligationsassociated with the payment credential includes accessing one or moredatabases to determine whether the payment credential is obligated for apayment having associated information stored in the one or moredatabases. The payment obligations may be associated with multiplefinancial institutions and/or payees. Accordingly, the system mayrequire access to multiple, disparate databases to determine whether aparticular payment credential has payment obligations. In someinstances, the system may determine payment obligations based ondetermining whether a transaction recurs on a regular basis (e.g., monthto month or week to week, etc.).

In some embodiments, determining the one or more payment obligationsassociated with the payment credential includes determining that thepayment credential has been used for one or more recurring transactionsfor two or more payment periods. In some such embodiments, determiningthat the payment credential has been used for one or more recurringtransactions for two or more payment periods includes determining thatthe payment credential has been used for two or more consecutive paymentperiods for a similar transaction comprising a similar transactionamount. In some of these embodiments, determining that the paymentcredential has been used for one or more recurring transactions for twoor more payment periods includes determining that the payment credentialhas been used for the same transaction amount for two or moreconsecutive payment periods.

In some embodiments, determining that the payment credential has beenused for one or more recurring transactions for two or more paymentperiods includes determining that the payment credential has been usedfor a transaction amount within a predetermined percentage threshold ofa similar previous payment period. In some embodiments, determining thatthe payment credential has been used for one or more recurringtransactions for two or more payment periods determining that thepayment credential has been used for a transaction amount within apredetermined percentage threshold of a corresponding payment periodfrom one year prior.

It will further be understood that a system as contemplated herein canbe configured to perform any of the portions of the process flows 600,700 and/or 800 upon or after one or more triggering events (which, insome embodiments, is one or more any of the portions of the processflows 600, 700 and/or 800). As used herein, “triggering event” refers toan event that automatically triggers the execution, performance, and/orimplementation of a triggered action, either immediately, nearlyimmediately, or sometime after (e.g., within minutes, etc.) theoccurrence of the triggering event. For example, in some embodiments,the system performing any of the portions of the process flows 600, 700and/or 800 is configured such that the system receiving an indication ofa compromised payment vehicle or a potential exposure to loss (thetriggering event) automatically and immediately or nearly immediatelytriggers the system to automatically (without human intervention)generate a token for facilitating or completing a pending purchasetransaction (the triggered action).

Also it will be understood that, in some embodiments, a predeterminedtime and/or the passage of a predetermined per any of the portions ofthe process flows 600, 700 and/or 800. Of course, any of the embodimentsdescribed and/or contemplated herein can involve one or more triggeringevents, triggered actions, automatic actions, and/or human actions.

In addition, it will be understood that, in some embodiments, a systemperforming any of the portions of the process flows 600, 700 and/or 800(and/or a user thereof) is configured to perform each portion of theprocess flows 600, 700 and/or 800 from start to finish, within moments,seconds, and/or minutes (e.g., within approximately 10-15 minutes,etc.). In some embodiments, any of the portions of the process flows600, 700 and/or 800 are performed in real time, in substantially realtime, and/or at one or more predetermined times. Further, it will beunderstood that the number, order, and/or content of any of the portionsof the process flows 600, 700 and/or 800 are exemplary and may vary. Itwill further be understood that the any of the portions of the processflows 600, 700 and/or 800 can be configured to perform any one or moreof the portions of any one or more of the embodiments described and/orcontemplated herein.

In various embodiments of the invention, transaction limits and/orthresholds may be used. For example, transaction limits may be used todetermine whether a payment credential has been exposed and/or whetherto approve or deny a transaction. If a transaction (e.g., transactioninformation) fails to meet a limit, the transaction may be denied.Alternatively, if a transaction (e.g., transaction information) meets alimit, then the transaction may be allowed.

While the system has been described as determining whether thetransaction meets the limits and thereby determining whether an exposurehas occurred, in some embodiments filters for determining exposure mayalso be responsive to transaction information. For example, exceptionsto filters may allow a transaction even if a filter is not met. In anembodiment, the system evaluates the transaction information todetermine: (1) does the transaction meet the limits; and (2) if thetransaction does not meet the limits, does the transaction qualify foran exception to the limits. If the system determines that a positiveresponse to either query, then transaction may be allowed.

In some embodiments, the exceptions are based at least in part upon thetransaction information. For example, the system may determine that atransaction does not meet a category limit because doing so would causethe token to exceed the category limit for the time period. In thisexample, however, the system also determines that the token is near,e.g., within one week, within three days, within one day, or the like,the expiration date of the token or the current evaluation period forthe token and that the token has remaining funds in a differentcategory. Given the short period of time remaining for the expenses tobe made, the system may determine that the transaction falls within anexception and allow the transaction. In another example, the system maydetermine that the user is outside of geographic limits defined by aroute. The system, however, determines that the user has conducted atransaction at the merchant frequently in the past and therefore allowsthe transaction based on the previous number of transactions at themerchant. These examples use multiple types of transaction information,e.g., the date of the transaction, the location of the transaction, thecategory of the transaction, the amount of the transaction, and thelike, to determine if the exceptions apply. In some embodiments, only asingle piece of transaction information applies. For example, the systemmay always permit transactions that are associated with a specificcategory, for example, emergency expenses. The system may always permittransactions at emergency rooms, doctors' offices, and the like.

In some embodiments, the exceptions are determined by the system and/orthe user. For example, the system may provide a list of exceptions basedon the user's transaction history. If the user has a favorite coffeeshop, the system may allow transactions at the coffee shop up to acertain amount even if the transaction would not meet a limit. The useror an administrator may provide exceptions based on location or othertransaction information. For example, the user may input exceptions thatallow transactions within a specific region, e.g., a city, that wouldnot be allowed outside of the specific region. The exceptions may bechanged at any time by the system or user.

The exceptions may be limited by frequency, amount, percentage of thelimit, or the like. For example, a transaction may qualify for anexception but only up to a certain percentage of the funds remaining ina related category. For example, a transaction may qualify for anexception because the expense period for the token is almost expired andthere are remaining funds in a first category. The system may permit atransaction in a second category up to some percentage (e.g., 50%) ofthe funds remaining in the first category.

The transaction-responsive limits are designed to provide flexibility tothe system and better serve the user. The transaction-responsive limitsmay be tailored to the user or generic to the token and/or system. Byproviding for transaction-responsive limits, the system allowstransactions that would otherwise be denied based on binary yes/nolimits when the transaction information indicates the appropriateness ofthe transaction.

Although many embodiments of the present invention have just beendescribed above, the present invention may be embodied in many differentforms and should not be construed as limited to the embodiments setforth herein; rather, these embodiments are provided so that thisdisclosure will satisfy applicable legal requirements. Also, it will beunderstood that, where possible, any of the advantages, features,functions, devices, and/or operational aspects of any of the embodimentsof the present invention described and/or contemplated herein may beincluded in any of the other embodiments of the present inventiondescribed and/or contemplated herein, and/or vice versa. In addition,where possible, any terms expressed in the singular form herein aremeant to also include the plural form and/or vice versa, unlessexplicitly stated otherwise. As used herein, “at least one” shall mean“one or more” and these phrases are intended to be interchangeable.Accordingly, the terms “a” and/or “an” shall mean “at least one” or “oneor more,” even though the phrase “one or more” or “at least one” is alsoused herein. Like numbers refer to like elements throughout.

As will be appreciated by one of ordinary skill in the art in view ofthis disclosure, the present invention may include and/or be embodied asan apparatus (including, for example, a system, machine, device,computer program product, and/or the like), as a method (including, forexample, a business method, computer-implemented process, and/or thelike), or as any combination of the foregoing. Accordingly, embodimentsof the present invention may take the form of an entirely businessmethod embodiment, an entirely software embodiment (including firmware,resident software, micro-code, stored procedures in a database, etc.),an entirely hardware embodiment, or an embodiment combining businessmethod, software, and hardware aspects that may generally be referred toherein as a “system.” Furthermore, embodiments of the present inventionmay take the form of a computer program product that includes acomputer-readable storage medium having one or more computer-executableprogram code portions stored therein. As used herein, a processor, whichmay include one or more processors, may be “configured to” perform acertain function in a variety of ways, including, for example, by havingone or more general-purpose circuits perform the function by executingone or more computer-executable program code portions embodied in acomputer-readable medium, and/or by having one or moreapplication-specific circuits perform the function.

It will be understood that any suitable computer-readable medium may beutilized. The computer-readable medium may include, but is not limitedto, a non-transitory computer-readable medium, such as a tangibleelectronic, magnetic, optical, electromagnetic, infrared, and/orsemiconductor system, device, and/or other apparatus. For example, insome embodiments, the non-transitory computer-readable medium includes atangible medium such as a portable computer diskette, a hard disk, arandom access memory (RAM), a read-only memory (ROM), an erasableprogrammable read-only memory (EPROM or Flash memory), a compact discread-only memory (CD-ROM), and/or some other tangible optical and/ormagnetic storage device. In other embodiments of the present invention,however, the computer-readable medium may be transitory, such as, forexample, a propagation signal including computer-executable program codeportions embodied therein.

One or more computer-executable program code portions for carrying outoperations of the present invention may include object-oriented,scripted, and/or unscripted programming languages, such as, for example,Java, Perl, Smalltalk, C++, SAS, SQL, Python, Objective C, JavaScript,and/or the like. In some embodiments, the one or morecomputer-executable program code portions for carrying out operations ofembodiments of the present invention are written in conventionalprocedural programming languages, such as the “C” programming languagesand/or similar programming languages. The computer program code mayalternatively or additionally be written in one or more multi-paradigmprogramming languages, such as, for example, F#.

Some embodiments of the present invention are described herein withreference to flowchart illustrations and/or block diagrams of apparatusand/or methods. It will be understood that each block included in theflowchart illustrations and/or block diagrams, and/or combinations ofblocks included in the flowchart illustrations and/or block diagrams,may be implemented by one or more computer-executable program codeportions. These one or more computer-executable program code portionsmay be provided to a processor of a general purpose computer, specialpurpose computer, and/or some other programmable data processingapparatus in order to produce a particular machine, such that the one ormore computer-executable program code portions, which execute via theprocessor of the computer and/or other programmable data processingapparatus, create mechanisms for implementing the steps and/or functionsrepresented by the flowchart(s) and/or block diagram block(s).

The one or more computer-executable program code portions may be storedin a transitory and/or non-transitory computer-readable medium (e.g., amemory, etc.) that can direct, instruct, and/or cause a computer and/orother programmable data processing apparatus to function in a particularmanner, such that the computer-executable program code portions storedin the computer-readable medium produce an article of manufactureincluding instruction mechanisms which implement the steps and/orfunctions specified in the flowchart(s) and/or block diagram block(s).

The one or more computer-executable program code portions may also beloaded onto a computer and/or other programmable data processingapparatus to cause a series of operational steps to be performed on thecomputer and/or other programmable apparatus. In some embodiments, thisproduces a computer-implemented process such that the one or morecomputer-executable program code portions which execute on the computerand/or other programmable apparatus provide operational steps toimplement the steps specified in the flowchart(s) and/or the functionsspecified in the block diagram block(s). Alternatively,computer-implemented steps may be combined with, and/or replaced with,operator- and/or human-implemented steps in order to carry out anembodiment of the present invention.

While certain exemplary embodiments have been described and shown in theaccompanying drawings, it is to be understood that such embodiments aremerely illustrative of and not restrictive on the broad invention, andthat this invention not be limited to the specific constructions andarrangements shown and described, since various other changes,combinations, omissions, modifications and substitutions, in addition tothose set forth in the above paragraphs, are possible. Those skilled inthe art will appreciate that various adaptations, modifications, andcombinations of the just described embodiments can be configured withoutdeparting from the scope and spirit of the invention. Therefore, it isto be understood that, within the scope of the appended claims, theinvention may be practiced other than as specifically described herein.

To supplement the present disclosure, this application furtherincorporates entirely by reference the following commonly assignedpatent applications:

U.S. patent Docket Number application Ser. No. Title Filed On6070US1.014033.2138 14/196,816 MANAGED DIGITAL Mar. 4, 2014 WALLETS6071US1.014033.2153 14/196,798 TOKEN COLLABORATION Mar. 4, 2014 NETWORK6071US2.014033.2154 14/196,802 FORMATION AND FUNDING Mar. 4, 2014 OF ASHARED TOKEN 6072US1.014033.2151 14/196,364 LIMITING TOKEN Mar. 4, 2014COLLABORATION NETWORK USAGE BY USER 6072US2.014033.2152 14/196,373LIMITING TOKEN Mar. 4, 2014 COLLABORATION NETWORK USAGE BY TOKEN6073US1.014033.2149 14/196,809 LIMITING THE USE OF A Mar. 4, 2014 TOKENBASED ON A USER LOCATION 6073US2.014033.2150 14/196,813 AUTHORIZING AMar. 4, 2014 TEMPORARY TOKEN FOR A USER 6074US1.014033.2148 14/196,030CONTROLLING TOKEN Mar. 4, 2014 ISSUANCE BASED ON EXPOSURE6075US1.014033.2146 14/196,292 FLEXIBLE FUNDING Mar. 4, 2014 ACCOUNTTOKEN ASSOCIATIONS 6075US2.014033.2147 14/196,350 ACCOUNT TOKEN Mar. 4,2014 ASSOCIATIONS BASED ON SPENDING THRESHOLDS 6076US2.014033.214514/196,653 CUSTOMER TOKEN Mar. 4, 2014 PREFERENCES INTERFACE6076US3.014033.2172 14/196,752 CREDENTIAL PAYMENT Mar. 4, 2014OBLIGATION VISIBILITY 6077US1.014033.2143 14/196,919 PROVIDING Mar. 4,2014 SUPPLEMENTAL ACCOUNT INFORMATION IN DIGITAL WALLETS6078US1.014033.2142 14/196,894 PROVIDING OFFERS Mar. 4, 2014 ASSOCIATEDWITH PAYMENT CREDENTIALS IN DIGITAL WALLETS 6078US2.014033.217914/196,869 PROVIDING OFFERS Mar. 4, 2014 ASSOCIATED WITH PAYMENTCREDENTIALS AUTHENTICATED IN A SPECIFIC DIGITAL WALLET6079US1.014033.2141 14/196,257 FOREIGN EXCHANGE Mar. 4, 2014 TOKEN6079US2.014033.2173 14/196,257 FOREIGN CROSS-ISSUED Mar. 4, 2014 TOKEN6080US1.014033.2140 14/196,545 DIGITAL WALLET Mar. 4, 2014 EXPOSUREREDUCTION 6080US2.014033.2174 14/196,460 MOBILE DEVICE Mar. 4, 2014CREDENTIAL EXPOSURE REDUCTION 6081US1.014033.2139 14/196,947 ATM TOKENCASH Mar. 4, 2014 WITHDRAWAL 6151US1.014033.002194 14/196,034 RESTORINGOR REISSUING Mar. 4, 2014 OF A TOKEN BASED ON USER AUTHENTICATION6152US1.014033.002195 14/196,405 TOKEN USAGE SCALING Mar. 4, 2014 BASEDON DETERMINED LEVEL OF EXPOSURE

What is claimed is:
 1. A computer program product for exposure reductionby token deactivation and new token issuance for comprehensive digitalwallet management platform, the computer program product comprising atleast one non-transitory computer-readable medium havingcomputer-readable program code portions embodied therein, thecomputer-readable program code portions comprising: an executableportion configured for allowing presentation of a digital walletmanagement interface based on an identification of access to anauthorized online session; an executable portion configured forinitiating presentation of the digital wallet management interface,comprising: initiating presentation of at least one digital wallet;initiating presentation of at least one representation of at least onepayment credential and at least one indication of which of the at leastone digital wallets are associated with each of the at least one paymentcredentials; and initiating presentation of a travel toggle switchconfigured for graphical manipulation by the user between at least afirst position and a second position, wherein the first positioncorresponds to the user not traveling and the second positioncorresponds to the user traveling; an executable portion configured fordeactivating an original payment token and issue a new payment token tothe at least one digital wallet, in response to the travel toggle switchmoving from the first position to the second position; and an executableportion configured for allowing for re-activation of the originalpayment token upon an indication of the travel toggle switch moving fromthe second position to the first position.
 2. The computer programproduct of claim 1, wherein the at least one representation of the atleast one payment credential comprises a graphical object representingthe at least one payment credential; wherein the at least onerepresentation of the at least one digital wallet comprises a graphicalobject representing the at least one digital wallet; wherein the atleast one indication comprises a graphical link between the graphicalobject representing the at least one payment credential and thegraphical object representing the at least one digital wallet.
 3. Thecomputer program product of claim 2, wherein the graphical linkcomprises an overlap of the graphical object representing the at leastone payment credential with the graphical object representing the atleast one digital wallet.
 4. The computer program product of claim 1,further comprising: an executable portion configured for receiving userinput selecting one of the at least one representations of the at leastone payment credentials; and an executable portion configured forreceiving user input selecting one of the at least one digital walletsfor association with the selected at least one payment credential. 5.The computer program product of claim 4, further comprising: anexecutable portion configured for initiating presentation of theselected payment credential and the selected digital wallet and at leastone indication of association between the selected payment credentialand the selected digital wallet.
 6. The computer program product ofclaim 1, further comprising: an executable portion configured forreceiving user input setting a usage limit for one of the at least onedigital wallets, wherein the usage limit is a threshold spending limitfor an aggregation of all the payment credentials associated with thedigital wallet.
 7. The computer program product of claim 6, wherein theusage limit is a threshold spending limit to be applied to each of thepayment credentials associated with the digital wallet individually. 8.The computer program product s of claim 1, wherein the interface isaccessed by a customer authenticated through an online banking sessionadministered by a financial institution also administering the digitalwallet.
 9. The computer program product of claim 1, wherein theinterface is accessed by a customer authenticated through a mobilebanking application session administered by a financial institution alsoadministering the digital wallet.
 10. A computer-implemented method forexposure reduction by token deactivation and new token issuance forcomprehensive digital wallet management platform, the method comprising:providing a computing system comprising a computer processing device anda non-transitory computer readable medium, where the computer readablemedium comprises configured computer program instruction code, such thatwhen said instruction code is operated by said computer processingdevice, said computer processing device performs the followingoperations: allowing presentation of a digital wallet managementinterface based on an identification of access to an authorized onlinesession; initiating presentation of the digital wallet managementinterface, comprising: initiating presentation of at least one digitalwallet; initiating presentation of at least one representation of atleast one payment credential and at least one indication of which of theat least one digital wallets are associated with each of the at leastone payment credentials; and initiating presentation of a travel toggleswitch configured for graphical manipulation by the user between atleast a first position and a second position, wherein the first positioncorresponds to the user not traveling and the second positioncorresponds to the user traveling; deactivating an original paymenttoken and issue a new payment token to the at least one digital wallet,in response to the travel toggle switch moving from the first positionto the second position; and allowing for re-activation of the originalpayment token upon an indication of the travel toggle switch moving fromthe second position to the first position.
 11. The computer-implementedmethod of claim 10, wherein the at least one representation of the atleast one payment credential comprises a graphical object representingthe at least one payment credential; wherein the at least onerepresentation of the at least one digital wallet comprises a graphicalobject representing the at least one digital wallet; wherein the atleast one indication comprises a graphical link between the graphicalobject representing the at least one payment credential and thegraphical object representing the at least one digital wallet.
 12. Thecomputer-implemented method of claim 11, wherein the graphical linkcomprises an overlap of the graphical object representing the at leastone payment credential with the graphical object representing the atleast one digital wallet.
 13. The computer-implemented method of claim10, wherein the computer processing device is further configured to:receive user input selecting one of the at least one representations ofthe at least one payment credentials; and receive user input selectingone of the at least one digital wallets for association with theselected at least one payment credential.
 14. The computer-implementedmethod of claim 13, wherein the computer processing device is furtherconfigured to: initiate presentation of the selected payment credentialand the selected digital wallet and at least one indication ofassociation between the selected payment credential and the selecteddigital wallet.
 15. The computer-implemented method of claim 10, whereinthe computer processing device is further configured to receive userinput setting a usage limit for one of the at least one digital wallets.16. The computer-implemented method of claim 10, wherein the interfaceis accessed by a customer authenticated through an online bankingsession administered by a financial institution also administering thedigital wallet.
 17. The computer-implemented method of claim 10, whereinthe interface is accessed by a customer authenticated through a mobilebanking application session administered by a financial institution alsoadministering the digital wallet.